Method and system for data extraction from a transaction system to an analytics system

ABSTRACT

The present invention provides a method and system for the automatic extraction of data from a transaction system to an analytics system, which is capable of handling large volumes of application data.

FIELD OF THE INVENTION

The present invention relates to the areas of computer software, software engineering and development. In particular, the present invention provides a method and system for extraction of data from an application on a transaction system to an analytics system. The method and system provides generic extraction services for arbitrary data types and is capable of handling voluminous data generation by avoiding the use of a middleware channel.

BACKGROUND INFORMATION

It is often desirable to retain records of business transactions for analytical purposes such as data mining. Recent developments in business software systems and architecture have provided this functionality in an automated fashion. FIG. 1 a shows a typical scenario. Customer 150 interacts with application 209 running on transaction system 110. From time to time application 209 may generate transaction data 115, which is to be saved to transaction system database 245. These “save” events provide a trigger for the extraction of data from application 209 on transaction system 110 to analytics system 105. As noted above, transaction data 115 is extracted to analytics system 105 for storage, processing or data-mining functions. Analytics system 105 includes database management system (“DBMS”) 130 and server 125. DBMS 130 provides storage of received transaction data 115, search functionality, etc. Server 125 provides processing capabilities for analyzing and processing transaction data 115 stored in DBMS 130.

A particular example of a transaction and analytics system is the collaborative behavior of an OLTP (“Online Transaction Processing”) system and an OLAP (“Online Analytical Processing”) system. OLTP refers to a type of computer processing in which a computer system responds immediately to user requests as opposed to batch processing. Each request is considered to be a transaction. An OLAP refers to a category of software tools that provides analysis of data stored in a database. OLAP tools enable users to analyze different dimensions of multidimensional data such as time series and trend analysis views. An OLAP often is used in data mining. Typically an OLAP includes a server, which sits between a client and a database management system (“DBMS”). The OLAP server understands how data is organized in the database and has special functions for analyzing the data.

A significant technical challenge concerns the mechanism through which transaction data 115 is to be made available (i.e., transported) to analytics system 105. Intelligent design of an architecture that permits flexible and efficient extraction of data from transaction system 110 to analytics system 105 may have a significant performance impact upon the interaction between transaction system 110 and analytics system 105. In particular, it is desirable that the chosen architecture provide generic extraction of arbitrary data types without requiring reprogramming on a case by case basis. In addition, it is important that the architecture accommodate the particular data load generated by the transaction system.

SUMMARY OF THE INVENTION

The present invention provides a generic extraction framework for extraction of data generated on a transaction system to an analytics system. The generic extraction framework allows extraction services to be efficiently created for arbitrary data types with the need for reprogramming on a case by case basis. In addition, the generic extraction framework obviates the need for the transmission of data using a middleware layer, and therefore provides an environment for transmission of high data volumes between a transaction and analytics system.

According to one embodiment of the invention an application developer using an application modeling environment may select data (e.g., transaction data) to be extracted from a software application to be run on the transaction system to the analytics system. The modeled application and the selection information are compiled against extraction services provided by the framework in order to provide these extraction services to the running application. An application generator generates both runtime extraction modules and data structures that provide for the extraction of data from the transaction system to the analytics system.

According to one embodiment, a framework class is provided that handless all tasks related to the extraction process. In addition, the application generator generates an extraction data structure that is utilized to maintain the extraction data. In order to enable the extraction process to operate within a preexisting architecture that includes an analytics adapter, a data source definition record is made accessible to the analytics adapter. The data source definition record maintains all the required information necessary to enable the extraction process to occur including the data source, extraction structure, application component and appropriate extraction modules.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 a shows a relationship between a transaction system and an analytics system.

FIG. 1 b shows a full upload phase, a delta initialization phase, and a delta upload phase.

FIG. 1 c shows a general architecture for the operation of a channel for transport of data generated by an application to a queue.

FIG. 2 a shows an architecture for extracting transaction data from an application running on transaction system to a queue.

FIG. 2 b illustrates the relationship between a transaction data container and a transaction database.

FIG. 3 depicts a relationship between an application, an application framework and an extraction framework according to one embodiment of the present invention.

FIG. 4 depicts a generic extraction framework according to one embodiment of the present invention.

FIG. 5 a depicts a full upload phase of an extraction process according to one embodiment of the present invention.

FIG. 5 b depicts a delta initialization phase of an extraction process according to one embodiment of the present invention.

FIG. 5 c depicts a delta upload phase of an extraction process according to one embodiment of the present invention.

FIG. 6 depicts a data format utilized in a resales order and tracking management (“RTCM”) system according to one embodiment of the present invention.

FIG. 7 shows a user interface provide by an application modeling environment to allow an application developer to specify particular qualifiers to be extracted to an analytics system.

FIG. 8 is a user interface screen for establishing a data source definition record according to one embodiment of the present invention.

DETAILED DESCRIPTION

The present invention provides a generic framework for performing extraction services from a transaction system 110 running any number of applications to an analytics system 105. The generic extraction framework provided by the present invention accommodates arbitrary data types without the need for reprogramming on a case by case basis. In addition, the generic extraction framework is able to handle significant data volumes as it provides data transport services from an application running on a transaction system to a queue (where it is stored for later uploading to an analytics system) without the use of a middleware layer.

The overall extraction process typically comprises a number of distinct phases or modes. FIG. 1 b shows a full upload phase, a delta initialization phase, and a delta upload phase. Before describing the overall operation of each phase, the general mode of communication between analytics system 105 and transaction system 110 will be described. Transaction system 110 includes, among other things, processor 215 b and transaction system database 245. Analytics system 105 includes, among other things, processor 215 a and metadata tables 255. Metadata tables 255 store metadata regarding transaction data generated on transaction system 110. Processor 215 a on analytics system 105 initiates RFC (“Remote Function Call”) via analytics adapter module. Analytics adapter module 240 provides a communication bridge between analytics system 105 and transaction system 110. The nature of RFC 245 is determined by information packages (i.e., 235 a, 235 b, 235 c).

Typically, each information package 235 a, 235 b, 235 c is associated with a particular phase of the extraction process. For example, 181 a depicts a full upload phase of an extraction process. During this phase based upon instructions in full upload information package 2345 a, processor 215 a on analytics system 105 executes RFC 245, which causes all data generated by application 209 to be extracted from transaction system 110 to analytics system 105. Extraction data is retrieved from transaction system database 245 and processed by selection module 225 and mapping module 227, and then transported to analytics system 105. The structure and function of selection and mapping modules 225 and 227 will become evident as the invention is further described. For now, it is sufficient to realize that selection module 225 and mapping module 227 perform some operations on transaction data stored in transaction database 245 so it is in a format suitable for analytics system 105. In addition, during full upload phase 181 a, metadata tables 255 on analytics system 105 are populated with information regarding transaction data to be extracted. Note that queue 285 on transaction system 110 is not utilized during full upload phase 181 a.

181 b shows a delta initialization phase of an extraction process. During delta initialization phase 181 b, processor 215 on analytics system 105 initiates RFC call 245 that establishes channel 229 on transaction system 110. Channel 229 will allow transport of transaction data 115 from application 209 to queue 285. The structure and nature of channel 229 will become evident as the invention is further described. In addition, during delta initialization phase 181 b, metadata tables 255 are populated.

Once delta initialization 181 b has occurred, application 209 may generate transaction data, which is then automatically transported to queue 285 via channel 229 for later upload to analytics system 105. Typically, transaction data stored in queue 285 represents changes (i.e., delta information) of the data that was already uploaded during full upload phase 181 a.

During delta upload phase 181 c, processor 215 executes RFC 245, which causes delta transaction data stored in queue 285 to be uploaded to analytics system 105.

As noted above, during delta initialization phase 181 b, channel 229 is established for transport of delta transaction data to queue 285. A significant performance issue concerns the efficiency and structure of channel 229.

FIG. 1 c shows a general architecture for the operation of a channel 229 for transport of data generated by an application 209 to a queue 285. Application 209 running on transaction system 110 generates transaction data 115. Transaction data 115 may be stored in transaction database 245, which typically is a relational database. In this case, transaction data 115 is mapped to tables (not shown) forming the structure of transaction system database 245. Service API 227 provides infrastructure and services to effectuate the extraction of transaction data from transaction system (i.e., data generated by application 209) to analytics system 105. Event handler 298 receives “save events” as transaction data 115 is written to transaction system database 245. Upon receiving these “save events”, event handler 298 calls various services provided by service API 227. The services provided by service API 227 cause the transmission of transaction data 115 so that it is available to analytics system 105 in a format compatible with analytics system 105.

A significant technical issue concerns the nature of channel 229 for transmission of transaction data 115 from application 209 to queue 285. A related technical issue concerns how transaction data 115 is to be prepared for insertion into queue 285 in a form that is appropriate for analytics system 105. These design choices may have a significant performance impact upon the extraction process.

For example, FIG. 2 a shows an architecture for extracting transaction data from transaction system application 209 running on transaction system 110 to queue 285 where it will ultimately be available for uploading to analytics system 105. As shown in FIG. 2 a, the process relies upon middleware 230 and transaction data container 205 for transmission of transaction data 115 to queue 285.

The architecture shown in FIG. 2 a assumes that a delta initialization phase 181 b has been completed and a channel 229 established. Application 209 generates transaction data 115, which is to be stored in transaction database 245. Event handler 298 detects save events 511 when transaction data 115 is written to transaction system database 245. Upon detection of save events, event handler 298 notifies processor 215 a, which intercepts transaction data 115 and initiates certain calls to service API 227, which cause transaction data 115 to be encapsulated in transaction data container 205. The exact structure of transaction data container is not important. However, it should be understood that with the architecture shown in FIG. 2 a, transaction data container 205 stores transaction data 115 in a complex format that has been abstracted from the underlying tables of transaction system database 245. This complex data format must ultimately be processed to generate a data format compatible with analytics system 105.

Transaction data container 205 is transmitted from application 209 through middleware 230. Service API 227 provides functions for transforming transaction data 115 stored in transaction data container 205 into flat file structure 121, which is compatible with analytics system 105. Transaction data 115 that has been converted to flat file structure 121 is stored in queue 285 for retrieval by analytics system 105 via RFC call 245. Among other functions, analytics adapter module 240 prepares data transaction data 115 for processing by transaction system 105. Analytics system 105 makes RFC call 245 to analytics adapter module 240 to perform upload of data in queue 285. Among other functions, analytics adapter module 240 performs functions for upload of data to analytics system 105.

The architecture shown in FIG. 2 has a number of limitations. First, the architecture does not accommodate generic transaction data 115. Because transaction data container 205 abstracts the underlying fields and tables of transaction system database 245, transaction data container 205 must be interpreted. FIG. 2 b illustrates the relationship between transaction data container 205 and transaction database 245. Transaction data container includes a number of segments 253(1)-253(N), which are mapped to tables 247 forming transaction database 245. Segments 253(1)-253(N) may span multiple tables in transaction database 245. In addition, the structure of transaction data container 205 typically will vary depending upon the nature of application 209. Because of the varying format of transaction data container 205 and its relationship to application 209 and transaction system database 245, algorithms for converting segments stored in transaction data container 205 must be re-written for different applications types of transaction data containers 205.

Furthermore, in a many scenarios, transaction system 110 may generate a significant amount of data. For example, in a resales order transaction system, high volumes of data are typically generated. Using the scenario shown in FIG. 2, the large volume of generated data containers 205 place significant bandwidth and resource demands on middleware 230. Thus, the extraction scheme shown in FIG. 2 is not appropriate for applications involving voluminous data generation. Another limitation with the scheme shown in FIG. 2 a is that there may exist particular application frameworks that do not utilize a data container 205.

FIG. 3 depicts a relationship between an application, an application framework and an extraction framework according to one embodiment of the present invention. Application framework 315 defines a common architecture for developing applications 209 by providing services and functionalities that may be invoked by application 209. Using application modeling environment 360, application developer 350 models application 209 against the constructs and services provided by application framework 315. Application 209 may invoke the services provided by application framework 315.

Extraction framework 310 provides services and functionality for performing extraction of data from transaction system 110 to analytics system 105. According to one embodiment of the present invention, application developer 350 may model application 209 to invoke extraction services provided by extraction framework 310.

Application modeling environment 360 generates metadata 317, which is processed by application generator 329. Metadata 317 includes information representing the modeling choices made by application developer 350. In particular, among other things, metadata 317 reflects the services to be invoked from application framework 315 and extraction framework 310. Application generator 329 receives metadata 317 and generates application 209. In particular, according to one embodiment, application generator 329 generates extraction data structure 320, extraction runtime components 330 and application runtime components 340.

Application runtime components 340 represent runtime files for executing application 209, and in particular those services associated with application framework 315. Application runtime components 340 may include runtime executable files, resources, etc. (e.g., DLL files, EXE files, Java Byte Code, etc.). Similarly, extraction runtime components 330 may include runtime files for executing extraction services provided by extraction framework 310. Extraction runtime components 330 include runtime executable files, resources, etc. (e.g., DLL files, EXE files, Java Byte Code).

As shown in FIG. 3, application generator also generates extraction data structure 320, which is used by extraction runtime components 330 to facilitate an extraction process. The nature of extraction runtime components 330 and extraction data structure 320 will become evident as the invention is further described.

FIG. 4 depicts a generic extraction framework according to one embodiment of the present invention. Generic extraction framework 402 allows for transport of arbitrary data types from application 209 running on transaction system 110 to queue 285, where it is made available to analytics system 105 for later uploading. Generic extraction framework 402 includes extraction support services 415, extraction classes 405 and complex data structure 410. Extraction support services 415 provides various services such as event handling and other low level services for performing generic extraction of transaction data 115 from transaction system 110 to analytics system 105. Extraction classes 405 provide various methods and data structures for providing generic extraction of data from application 209 running on transaction system 110 to analytics system 105. Complex data structure 410 provides a data structure for storing extraction data in an intermediate stage before transaction data 115 is placed in queue 285. As will become evident as the invention is further described because complex data structure 410 assumes a structure compatible with transaction data container 205, it allows for the transfer of transaction data 115 to queue 285 using preexisting services of service API 227. The structure and function of extraction classes 405 and complex data structure will become evident as the invention is further described.

FIG. 4 also shows corresponding extraction runtime components 330 including extraction event handler 435, extraction objects 445 and complex data structure 410. Extraction event handler 435 provides event handling services specifically designed for performing generic extraction functions from application 209 running on transaction system 209 to analytics system 105. Extraction objects 445 represent instantiated extraction classes 405 existing at runtime.

According to one embodiment of the present invention, extraction event handler 435 detects events occurring with respect to application 209. Upon detection of particular events, extraction event handler 435 causes particular actions to occur. The function of extraction event handler 435 will become evident as the invention is further described. According to one embodiment of the present invention, event handler 435 detects save events whereby transaction data 115 is written to transaction system database 245.

The generic extraction framework according to the present invention may be stored as a set of instructions that is accessible and executable by a processor. This set of instructions may stored in a storage subsystem that may include a compact disk, hard drive, DVD-ROM, CD-ROM or any type of computer- or machine-readable storing medium.

FIGS. 5 a-5 a describe a full upload phase, a delta initialization phase and a delta upload phase of an extraction process according to one embodiment of the present invention.

FIG. 5 a depicts a full upload phase of an extraction process according to one embodiment of the present invention. Datasource definition record 525 is provided to analytics system 165. Among other things, datasource definition record 525 provides analytics system 105 with information regarding selection 225 and mapping 227 modules that are to be executed on transaction system. The structure and function of datasource definition record 525, selection 225 and mapping 227 modules will be described below. For now it is sufficient to realize that datasource definition record 525 provides analytics system 105 with certain information regarding the invocation of an extraction processes on transaction system 110. During the full upload phase, analytics system 165 executes RFC 245 to transaction system 110 via analytics adapter module 240. RFC call 245 is established via full upload information package 225 a.

RFC call 245 causes transaction data stored in transaction system database 245 to be extracted from transaction system database 245 and processed by selection 225 and mapping 227 modules. Selection module 225 determines the data stored in transaction system database 245 that is to be extracted from transaction system database 245. As noted above, the selection of data to be extracted from transaction system 110 to analytics system 105 is established during application modeling (i.e., see FIG. 3). An exemplary user interface for selection of data to be extracted will be described below. Mapping module 227 performs transformation on data stored in transaction system database 245 into a form that is compatible with analytics system 165. Exemplary selection and mapping processes are described in detail below.

Once transaction data stored in transaction system database 245 is processed by selection module 225 and mapping module 227, it is passed to analytics adapter 240 where it is uploaded to analytics system 165 and stored in DMBS 130. In addition, during the full upload process, metadata tables 255 on analytics system 105 are populated with information regarding the transaction data 115 that is to be extracted to analytics system 105.

FIG. 5 b depicts a delta initialization phase of an extraction process according to one embodiment of the present invention. Analytics system 105 executes RFC call 245 via analytics adapter module. RFC call 245 causes processor 215 a to establish channel 229 through which extraction data 115 may flow from application 209 to queue 285. Once channel 229 has been established, a path exists for the flow of transaction data 115 generated by application 209 to queue 285. In particular, as shown in FIG. 2 b, when application 209 is running, save event 511 is detected by extraction event handler 445 (i.e., transaction data 115 is saved to transaction system database 245). Extraction event handler 445 makes appropriate method calls to extraction objects 445 to cause population of complex data structure 410. Complex data structure 410 is then provided via established channel 229 to queue 285 via a call to a queue loading service provided by service API 227.

FIG. 5 c depicts a delta upload phase of an extraction process according to one embodiment of the present invention. As shown in FIG. 5 c, transaction data representing delta information that was previously stored in queue 285 during running of application 209 is uploaded to analytics system. In particular, as shown in FIG. 5 c, processor 215 a on analytics system utilizes delta upload information package 235 c to make RFC call 245 to transaction system 110 via analytics adapter module 240.

Processor 215 b then makes call to analytics adapter module 240 to cause delta transaction data stored in queue 285 to analytics system 105. Data received at analytic system 105 is stored in DBMS 130 where it is available for further processing, analytics, refinement, etc.

According to one embodiment a generic extractor classes 405 handle all tasks related to the extraction process. According to one embodiment, an extraction class 405 CL_CMS_LO_BW_APPL_EXTRACT has the following methods:

CMS_LO_BW_GET_TIME_INTERVAL

This method provides information regarding when was the last time the analytics system was updated with data using the datasource.

CMS_LO_BW_UPDATE_TIME_INTERVAL

This method updates the information about the time when the update using the datasource is performed.

CMS_LO_BW_EXTRACT

The method performs the actual fetch of the data on the basis of the selection options in form of data packets. This method does not use the time stamp approach to handle the delta update requirements. It works on the premise that the delta queues would be directly updated with changed data after the initial upload.

CMS_LO_BW_EXTRACT_DELTA

The method performs the actual fetch of the data on the basis of the selection options in form of data packets. This method uses the time stamp approach to handle the delta update requirements. It works on the premise that the delta queues would be updated with changed data after the initial upload using the timestamps of the previous upload being maintained in the timestamps table.

CMS_LO_BW_MAPPER

This method is used to map the complex data into a flat structure so that it can be moved across to analytics system 105.

LOG_WRITE

This method is used to log exceptions to a log.

According to one embodiment, the CMS_LO_BW_EXTRACT method has the following signature: VALUE( I_PACKSIZE ) TYPE I VALUE( I_FIRST_CALL ) TYPE RSAAPI_IF- INITFLAG VALUE( APPL_NAME ) TYPE Lean order CMST_APPLICATION application code I_GT_WHERE TYPE TABLE OPTIONAL I_T_SEGMENTS TYPE TABLE OPTIONAL I_T_FIELDS TYPE TABLE OPTIONAL I_T_SMOSEL TYPE TABLE I_UPDMODE TYPE SBIWA_S_INTERFACE- UPDMODE OPTIONAL I_REQUNR TYPE SBIWA_S_INTERFACE- REQUNR OPTIONAL E_DATA TYPE ANY E_T_RETURN TYPE TABLE OPTIONAL NO_MORE_DATA There is no more data available to transfer. ERROR_PASSED_(—) Error has TO_MESS_HANDLER been passed on to the appropriate message handler.

According to one embodiment, the CMS_LO_BW_MAPPER method has the following signature: EXTRACT DATA TYPE ANY Mapped data I_DATA TYPE ANY Extracted data APPL_NAME TYPE Lean order application CMST_APPLICATION code MAP_ERROR Mapping error

According to one embodiment of the present invention, selection module 225 is implemented as follows.

Selection Module Template *″---------------------------------------------------------------------- *″*″Local interface: *″ IMPORTING *″ REFERENCE(I⁻PACKSIZE) TYPE I *″ REFERENCE(I⁻FIRST⁻CALL) TYPE RSAAPI⁻IF-INITFLAG *″ EXPORTING *″ REFERENCE(E⁻DATA) *″ TABLES *″ I⁻GT⁻WHERE OPTIONAL *″ I⁻T⁻SEGMENTS STRUCTURE  SMOXSEGMS OPTIONAL *″ I⁻T⁻FIELDS STRUCTURE  SMOXFIELDS OPTIONAL *″ I⁻T⁻SMOSEL STRUCTURE  SMOBWASEL OPTIONAL *″ E⁻T⁻RETURN STRUCTURE  BAPIRET2 OPTIONAL *″ EXCEPTIONS *″ NO⁻MORE⁻DATA *″ OPEN⁻CURSOR⁻ERROR *″ CURSOR⁻ALREADY⁻EXISTS *″ CURSOR⁻DOES⁻NOT⁻EXIST *″---------------------------------------------------------------------- *+<BEGIN> *+COM FUNCTION <FUNCNAME>. *+COM*″--------------------------------------------------------------------- - *+COM*″*″Local interface: *+COM*″ IMPORTING *+COM*″ REFERENCE(I⁻PACKSIZE) TYPE I *+COM*″ REFERENCE(I⁻FIRST⁻CALL) TYPE RSAAPI⁻IF-INITFLAG *+COM*″ EXPORTING *+COM*″ REFERENCE(E⁻DATA) TYPE <BW⁻STR⁻C> *+COM*″ TABLES *+COM*″ I⁻GT⁻WHERE OPTIONAL *+COM*″ I⁻T⁻SEGMENTS STRUCTURE  SMOXSEGMS OPTIONAL *+COM*″ I⁻T⁻FIELDS STRUCTURE  SMOXFIELDS OPTIONAL *+COM*″ I⁻T⁻SMOSEL STRUCTURE  SMOBWASEL OPTIONAL *+COM*″ E⁻T⁻RETURN STRUCTURE  BAPIRET2 OPTIONAL *+COM*″ EXCEPTIONS *+COM*″ NO⁻MORE⁻DATA *+COM*″ OPEN⁻CURSOR⁻ERROR *+COM*″ CURSOR⁻ALREADY⁻EXISTS *+COM*″ CURSOR⁻DOES⁻NOT⁻EXIST *+COM*″--------------------------------------------------------------------- - *+COM *+COM TYPE-POOLS: *+COM RSAOT, *+COM RSDS, *+COM SBIWA. *+COM *+COM CONSTANTS: *+COM lc⁻requnr TYPE sbiwa⁻s⁻interface-requnr *+COM VALUE space, *+COM lc⁻appl⁻name TYPE cmst⁻application VALUE ′<APPL>′, *+COM lc⁻logsys TYPE TBDLS-LOGSYS VALUE space, *+COM lc⁻updmode TYPE SBIWA⁻S⁻INTERFACE-UPDMODE VALUE ′F′. *+COM *+COM DATA: *+COM lv⁻initflag TYPE sbiwa⁻s⁻interface-initflag, *+COM lv⁻maxsize TYPE sbiwa⁻s⁻interface-maxsize. *+COM *+COM STATICS: *+COM ls⁻select TYPE LINE OF sbiwa⁻t⁻select, *+COM lt⁻select TYPE sbiwa⁻t⁻select. *+COM *+COM *+COM DATA: *+COM lv⁻myclass TYPE REF TO cl⁻cms⁻lo⁻bw⁻appl⁻extract. *+COM *+COM STATICS: lv⁻per⁻myclass TYPE REF TO cl⁻cms⁻lo⁻bw⁻appl⁻extract. *+COM *+COM IF lv⁻per⁻myclass IS INITIAL. *+COM CREATE OBJECT lv⁻myclass. *+COM lv⁻per⁻myclass = lv⁻myclass. *+COM ENDIF. *+COM *+COM*----- Parameter passing -------------------------------------------* *+COM lv⁻initflag = i⁻first⁻call. *+COM lv⁻maxsize = i⁻packsize. *+COM *+COM IF lv⁻initflag < > space. *+COM LOOP AT i⁻t⁻smosel. *+COM MOVE-CORRESPONDING i⁻t⁻smosel TO ls⁻select. *+COM APPEND ls⁻select TO lt⁻select. *+COM ENDLOOP. *+COM ENDIF. *+COM *+COM*----- Call to generic extractor -------------------------------------- -----* *+COM *+COM CALL METHOD lv⁻per⁻myclass->cms⁻lo⁻bw⁻extract *+COM EXPORTING *+COM i⁻packsize = i⁻packsize *+COM i⁻first⁻call = lv⁻initflag *+COM appl⁻name = lc⁻appl⁻name *+COM i⁻t⁻smosel = lt⁻select *+COM I⁻UPDMODE = lc⁻updmode *+COM I⁻REQUNR = lc⁻requnr *+COM IMPORTING *+COM E⁻DATA = e⁻data *+COM EXCEPTIONS *+COM NO⁻MORE⁻DATA = 1 *+COM ERROR⁻PASSED⁻TO⁻MESS⁻HANDLER = 2 *+COM others = 3. *+COM *+COM IF sy-subrc = 1. *+COM RAISE NO⁻MORE⁻DATA. *+COM EXIT. *+COM ELSEIF sy-subrc = 2. *+COM RAISE OPEN⁻CURSOR⁻ERROR. *+COM EXIT. *+COM ELSEIF sy-subrc > 2. *+COM MESSAGE e00l (CMS⁻BW⁻MSG). *+COM EXIT. *+COM ENDIF. *+COM *+COM *+COM  ENDFUNCTION. *+<END>

The following is pseudo-code for selection module 225 according to one embodiment of the present invention:

-   1. Create the instance of the generic extractor class     cl_cms_lo_bw_appl_extract. -   2. If lv_initflag is not initial.     -   Loop at the input selection options.     -   Append the input selection options to the selection options         table. Endif. -   3. Use the generic extractor instance to call the extraction method.

According to one embodiment of the present invention, mapping module 227 is implemented as follows.

Mapping Module Template *″----------------------------------------------------------------------- *″″Local interface: *″ IMPORTING *″ REFERENCE(I⁻DATA) *″ TABLES *″ EXTRACT⁻DATA *″ EXCEPTIONS *″ MAP⁻ERROR *″ ENTRY⁻NOT⁻FOUND *″----------------------------------------------------------------------- *+<BEGIN> *+COM FUNCTION <FUNCNAME>. *+COM*″---------------------------------------------------------------------- - *+COM*″*″Local interface: *+COM*″ IMPORTING *+COM*″ VALUE(I⁻DATA) TYPE <BW⁻STR⁻C> *+COM*″ TABLES *+COM*″ EXTRACT⁻DATA STRUCTURE CMST⁻RTCM⁻BW *+COM*″ EXCEPTIONS *+COM*″ MAP⁻ERROR *+COM*″ ENTRY⁻NOT⁻FOUND *+COM*″---------------------------------------------------------------------- - *+COM *+COM DATA: lv⁻myclass TYPE REF TO cl⁻cms⁻lo⁻bw⁻appl⁻extract. *+COM *+COM STATICS: lv⁻per⁻myclass TYPE REF TO cl⁻cms⁻lo⁻bw⁻appl⁻extract. *+COM *+COM DATA: lc⁻appl⁻name TYPE cmst⁻application VALUE ′<APPL>′. *+COM *+COM IF lv⁻per⁻myclass IS INITIAL. *+COM CREATE OBJECT lv⁻myclass. *+COM lv⁻per⁻myclass = lv⁻myclass. *+COM ENDIF. *+COM *+COM CALL METHOD lv⁻per⁻myclass ->cms⁻lo⁻bw⁻mapper *+COM EXPORTING *+COM i⁻data = i⁻data *+COM appl⁻name = lc⁻appl⁻name *+COM IMPORTING *+COM extract⁻data = extract data[] *+COM EXCEPTIONS *+COM map⁻error = 1 *+COM OTHERS = 2. *+COM IF sy-subrc < > 0. *+COM RAISE map⁻error. *+COM ENDIF. *+COM *+COM  ENDFUNCTION. *+<END>

The following is pseudo-code for selection module 225 according to one embodiment of the present invention:

-   -   1. If no class instance exists.         -   a. Create class cl_cms_lo_bw_appl_extract instance. Endif.     -   2. Call the mapper method using the class instance.

According to one embodiment, application generator 515 utilizes the following interface, which interprets the selection module template and mapping module template shown above. *″---------------------------------------------------------------------- *″*″Local interface: *″ IMPORTING *″ REFERENCE(IV⁻APPLICATION) TYPE CMST⁻APPLICATION *″ EXCEPTIONS *″ BW⁻STR⁻NOT⁻FOUND *″ ERROR *″----------------------------------------------------------------------

FIG. 6 depicts a data format utilized in a resales order and tracking management (“RTCM”) system according to one embodiment of the present invention. The framework shown in FIG. 6 represents one example in which the present invention may be applied. It will be understood by skilled practitioners that the present invention may be utilized to provide a framework for data extraction from an application to an analytics system wherein the application utilizes any type of framework architecture. With respect to the exemplary application (a resales order system), datasets include partner 610, price 620, document 630, quantity 640, product 650 and dates 660. A qualifier represents different instances of a particular data set. For example, all partners relevant for a business process implemented using the resales order (“RO”) are the partner qualifiers. The qualifiers are typically independent of the applications comprising a business process. To model an application, the relevant qualifiers are grouped as profiles, which are attached to an application. Thus, for an application such as RTCM of the Channel Sales business scenario there could exist six profiles 615, 625, 635, 645, 655 and 665 mapping respectively to a particular data set 615, 625, 635, 645, 655 and 665. Each of these profiles has a set of qualifiers attached to them.

FIG. 7 shows a user interface provide by application modeling environment 360 to allow application developer 350 to specify particular qualifiers to be extracted to analytics system 105. Application modeling window 720 shows profile qualifier field 705, which display particular profile qualifiers (see FIG. 6). Application modeling window 720 also includes BW Rel field 710, which allows application developer to select particular profile qualifiers for extraction to analytics system 105.

FIG. 8 is a user interface screen for establishing a data source definition record according to one embodiment of the present invention. Data source definition record 525 will include data source field 810, BDoc field 820, extraction structure field 830, application component field 840 and selection module field 850 and mapping module field 860.

Data source field identifies a name of the data source definition record. Extraction structure 830 identifies the name of the extraction data structure 320 generated by application generator 515. Application component 840 identifies the associated application component 209 for which data extraction is to occur. Selection and mapping modules 850 and 860 respectively identify the extraction and mapping modules (225, 227).

Normally, BDoc field 830 would identify a transaction data container type 205 for transmitting data from a transaction system 110 to analytics system 105. However, the present invention provides a method for extraction without the use of a transaction data container 205 and is left blank.

The following is an exemplary set of fields for inclusion in a data source definition record 525 according to one embodiment of the present invention. Data source 0CMS_RTCM_TRAN Extract Struct. CMST_RTCM_BW Type of DataSource TRAN Appl. Component 0CMS_RTCM Delta Procedure AIMD Delete Fld:Name RECORDMODE SelectionModule CMS_RTCM_BW_SEL Mapping Module CMS_RTCM_BW_MAP

A method and system for extraction of data to an analytics system has been described. The present invention provides a method for extraction of data from an application to an analytics system using a generic extraction data structure generated during application generation. This method eliminates the need for an event driven middleware approach and is thus suitable for environments in which large amounts of data are generated.

Several embodiments of the invention are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations of the invention are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention. 

1. A method for extracting data from a software application to an analytics system comprising: receiving extraction information identifying data to be extracted to the analytics system; generating an application as a function of the extraction information data, wherein the application includes: a data structure for storing extraction data; and at least one component for performing an extraction function to prepare data for processing by the analytics system; and configuring the analytics system to invoke the at least one component performing an extraction function at at least one predetermined time.
 2. The method according to claim 1, wherein the at least one component includes a selection module.
 3. The method according to claim 1, wherein the at least one component includes a mapping module.
 4. The method according to claim 1, wherein the data structure is a complex data structure.
 5. The method according to claim 4, wherein the at least one component transforms the complex data structure to a flat file structure.
 6. The method according to claim 1, wherein the application is an online transaction processing (“OLTP”) system.
 7. The method according to claim 1, wherein the analytics system is an online analytics processing (“OLAP”) system.
 8. A system for extracting data from a software application to an analytics system comprising: a processor, the processor providing an application modeling environment for: receiving extraction information identifying data to be extracted to the analytics system; generating an application as a function of the extraction information data, wherein the application includes: a data structure for storing extraction data; and at least one component for performing an extraction function to prepare data for processing by the analytics system; and configuring the analytics system to invoke the at least one component performing an extraction function at at least one predetermined time.
 9. The system according to claim 8, wherein the at least one component includes a selection module.
 10. The system according to claim 8, wherein the at least one component includes a mapping module.
 11. The system according to claim 8, wherein the data structure is a complex data structure.
 12. The system according to claim 11, wherein the at least one component transforms the complex data structure to a flat file structure.
 13. A program storage device, the program storage device including instructions for: receiving extraction information identifying data to be extracted to the analytics system; generating an application as a function of the extraction information data, wherein the application includes: a data structure for storing extraction data; and at least one component for performing an extraction function to prepare data for processing by the analytics system; and configuring the analytics system to invoke the at least one component performing an extraction function at at least one predetermined time.
 14. The program storage device according to claim 13, wherein the at least one component includes a selection module.
 15. The program storage device according to claim 13, wherein the at least one component includes a mapping module.
 16. The program storage device according to claim 13, wherein the data structure is a complex data structure.
 17. The program storage device according to claim 13, wherein the at least one component transforms the complex data structure to a flat file structure.
 18. A machine-readable medium storing a generic extraction framework for extraction data generated by an application to an analytics system comprising: a generic extraction class, the generic extraction class providing services for population of a complex data structure as a function of transaction data generated by the application; a data handler configured to transport data stored in the complex data structure to a buffer for uploading to the analytics system; an extraction data structure, comprising a complex data type; and an event handler configured to detect a generation of transaction data by the application and to invoke at least one method of the generic extraction class.
 19. The machine-readable medium of claim 18, wherein the buffer is a queue.
 20. The machine-readable medium of claim 19, wherein the complex data structure is compatible with a data container designed to utilize a middleware for the transmission of transaction data from the application to the buffer.
 21. The machine-readable medium of claim 20, wherein the generic extraction class invokes at least one method call to a service expecting the passing of a transaction data container, but instead passes the complex data structure. 